Sql项目管理 - #6170

- Add canonicalize_within_root to detect symlink traversal; wire into 5 file operation commands

- Add 7 symlink regression tests (create, existing file, rename, delete, normal path, nonexistent target, nested)

- Extract useFolderWatcherLifecycle composable: only active project watches, switch drops old/creates new, focus rescans active only

- Replace full-project watcher logic in SqlFilePanel.vue with lifecycle composable

- Add 15 unit tests for watcher lifecycle (init, switch, focus, cleanup)

- Pin trash dependency to 5.2

- Resolve file-op root from project_id via find_sql_project_by_id, rejecting untrusted projects

- Replace canonicalize_within_root with validate_within_root (validation only); file ops use lexical paths

- Use create_new/create_dir atomics to close the TOCTOU window between validation and write

- Add internal symlink regression tests

- Fix watcher async race with pendingWatchers set

- Normalize root path case-insensitively on Windows only

externalSqlFileTargetPersistence.test.ts now asserts the meta-object catalog field instead of the removed positional argument; list_sql_files.rs compares names character-by-character so proc.sql sorts before proc1.sql.

# Conflicts:
#	apps/desktop/src/components/layout/SqlFilePanel.vue

- treat bound project connection/schema as authoritative at all open entry points
- bind and verify stable root identity to prevent symlink escape
- keep failed legacy folder migrations; migrate snapshot paths on rename
- lazy-load Local History snapshots and only scan the active project
- replace system trash with DBX-managed trash (restore/empty with rollback)

…test

cap-std's Dir::try_exists returns Ok(false) for a missing path instead of
Err, so the old is_err() assertions always failed on Linux CI. Assert the
handle remains usable by expecting false for a nonexistent entry.

…e-and-recreate

(dev, ino) alone cannot detect same-path delete-and-recreate: Linux ext4
reuses inodes, so a recreated directory matches the recorded identity. Write
a hidden marker file (.dbx-root-identity, random token) inside the project
root when establishing identity and verify it on every resolve; a recreated
or replaced root loses the marker and is rejected deterministically.

- RootIdentity gains marker field (serde skip when None, legacy rows keep
  working); no DB migration needed (identity is stored as JSON)
- read_project_root_identity establishes/reuses the marker (read-only roots
  degrade to marker-less identity)
- root_identity_matches() checks (dev, ino)+fallback then marker content
- new test resolve_trusted_root_rejects_deleted_marker
- make delete-and-recreate test deterministic (no longer inode-reuse flaky)